Update to the latest Legion#1007
Conversation
|
@manopapad Tests seem to be failing with the latest Legion. |
|
I am seeing the following:
The most problematic tests appear to be:
I was able to reproduce some of these heap corruptions on computelab, here are the backtraces I was able to get: Heap corruption backtraces@lightsighter before we go digging any further, are you aware of any change in Legion between commits a2ec81dde867e542b335ea98826475f8d601c2ad and 70f9fbbce07ec4772696c57036d5fc7f84ea264d that could be causing this heap corruption? |
|
Have you tried turning off the caching allocator? |
That didn't fix it |
|
|
|
Here is a backtrace for some invalid reads that are occuring: I can't explain why they are happening though since I don't know how to pass @sgurfinkel for visibility. |
|
I updated to the latest Legion, and fewer tests seem to fail. |
But there are still failing tests right? I think that the fundamental problem is still there (whatever it is). |
|
I'm going to take this opportunity to test a change to the test configuration, whereby we tell pytest to not install python's signal handler, which tends to shadow Realm's printing of C++ backtraces. Hopefully this results in more informative backtraces when the C++ side crashes. |
It conflicts with pytest's "-p no:faulthandler"
|
/ok to test |
|
@marcinz it looks like tests passed, so I think we can merge this and nv-legate/legate#803 |
For testing, this PR points to the PR version of legate.core. Before merge, the version of legate.core should be changed to the commit on the legate.core dev branch.